Exchanging information between devices in a medical environment

ABSTRACT

A medical device including an operation determiner for determining operations to be performed by the medical device in response to a gesture of the device with respect to the medical device, and an operation data accessor for accessing operation data for the operation performed by the medical device.

CROSS-REFERENCE TO RELATED U.S. APPLICATIONS

This Application is related to U.S. patent application Ser. No.13/015,515, entitled, “Associating Devices in a Medical Environment” byHalbert et al., with filing date Jan. 27, 2011, and assigned to theassignee of the present invention.

BACKGROUND

Typically, association of a medical device with another device requiresmultiple data entries and screen navigations by a user of the medicaldevice (e.g., clinician). For example, sending a medication order from adevice to a specific infusion pump requires multiple steps related to(1) association of the device to the medical device, and (2) initiatinga transfer of medication orders.

Moreover, a clinician may have to navigate through multiple screens totrigger a specific activity on the medical device. For example, if aclinician wants to view the last medication administration time on adevice, the clinician selects multiple screens, screen controls andinput data.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example of a medical environment, in accordancewith an embodiment of the present invention.

FIGS. 2 and 3 illustrate examples of devices, in accordance withembodiments of the present invention.

FIG. 4 illustrates an example of a method for associating a medicaldevice with a second device, in accordance with an embodiment of thepresent invention.

FIG. 5 illustrates an example of a method for performing an operation bya medical device, in accordance with an embodiment of the presentinvention.

The drawings referred to in this description should be understood as notbeing drawn to scale except if specifically noted.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments of the presenttechnology, examples of which are illustrated in the accompanyingdrawings. While the technology will be described in conjunction withvarious embodiment(s), it will be understood that they are not intendedto limit the present technology to these embodiments. On the contrary,the present technology is intended to cover alternatives, modificationsand equivalents, which may be included within the spirit and scope ofthe various embodiments as defined by the appended claims.

Furthermore, in the following description of embodiments, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present technology. However, the present technologymay be practiced without these specific details. In other instances,well known methods, procedures, components, and circuits have not beendescribed in detail as not to unnecessarily obscure aspects of thepresent embodiments.

Embodiments of Associating a Medical Device and Another Device

FIG. 1 depicts an embodiment of medical system environment 100. Medicalsystem environment 100 includes devices 110 and 210, and optionallymedical management system 112. For example, devices 110 and 220 are ableto wirelessly communicate with one another. Optionally, devices 110 and220 are able to wirelessly communicate with medical management system112.

In various embodiments, one of the devices 110 or 210 is a medicaldevice (e.g., respirators, vital sign monitors, medication deliverysystems, etc) and the other device is a mobile device (personal digitalassistant (FDA), smart phone, cell phone, etc). Typically, (1) a medicaldevice is any medical device that administers care to a patient, and (2)a mobile device is any mobile device that is able to be associated withthe medical device and subsequently exchange information with themedical device to facilitate in the administration of care to thepatient. In another embodiment, both devices 110 and 210 are medicaldevices. Moreover, the medical device and the mobile device include thecapabilities to detect and communicate occurrences of gestures betweenthe devices, which will be described in detail below.

When devices 110 and 210 are unassociated with one another, they areunable to exchange information with one another. However, onceassociated, devices 110 and 210 are able to exchange information withone another. Accordingly, devices 110 and 210 must be associated suchthat they properly and safely exchange information with one another,which will be described in detail below.

The following discussion will first describe the components and/orfeatures of devices 110 and 210 in medical environment 100. Then thediscussion will describe the functionality of the components and/orfeatures during use of the devices in the medical environment. Inparticular, the discussion will describe the functionality of thecomponents and/or features regarding the association of the medicaldevices.

Referring to FIGS. 1 and 2, device 110 includes gesture sensor 115,association gesture determiner 120, associator 130, user interface 150,wireless communication module 145, memory 158, and optionally proximitydeterminer 140.

Gesture sensor 115 is for sensing or detecting a gesture of device 210with respect to device 110. A gesture is a device movement and/oractivity associated with the device for the intent of association of thedevice with another device. The gesture is detected within a short timewindow, such as a predefined short time window.

In various embodiments, gesture sensor 115 can be, but is not limitedto, an accelerometer, gyroscope, etc. In one embodiment, gesture sensor115 is an input sensor that senses a key press or a touch of a sensor.For example, if devices 110 and 210 do not have accelerometers orgyroscope, a user can generate a gesture by pressing a key on either orboth devices within a short time window.

Association gesture determiner 120 is for determining that the gestureis an association gesture. An association gesture is a gestureinitiating a request to associate devices 110 and 210, which will bedescribed in further detail below.

Association gesture determiner 120 includes filter 122. Filter 122 isfor filtering out unauthorized gestures or gestures which are notintended to initiate a request to associate devices 110 and 210.

Associator 130 includes device associator 132, clinician associator 134and patient associator 136.

Device associator 132 is for associating/disassociating devices 110 and210 based on the association gesture. Device associator 132 includesassociation request validator 133.

Association request validator 133 is for validating the associationrequest (via the association gesture) based on information communicatedbetween devices 110 and 210.

Clinician associator 134 is for associating/disassociating a clinicianor device user with device 110. Patient associator 136 is forassociating/disassociating a patient with device 110.

Proximity determiner 140 is for determining a proximity between devices110 and 210. Proximity determiner 140 can detect proximity by utilizingRF signal strength, relative distance measurements using a globalpositioning system (GPS) or other location determining technologies.

Wireless communication module 145 is for wirelessly communicatinginformation between devices 110 and 210, and optionally with medicalmanagement system 112. In various embodiments, the wirelesscommunication is radio frequency (RF) communication (e.g., Bluetooth,WiFi, ZigBee, WiFi direct, etc).

FIG. 3 depicts an embodiment of device 210. Similar to device 110,device 210 includes gesture sensor 215, association gesture determiner220, associator 230, proximity determiner 240, user interface 250,wireless communication module 245 and memory 258.

The components included in device 210 are the same components andfunction similarly as the components of device 110. However, for brevityand clarity, the description herein will focus on the components ofdevice 110.

As described above, devices 110 and 210 have to be associated with oneanother before they can communicate information with one another.

To request or initiate an association between devices 110 and 210,device 210 is moved to create a gesture with respect to device 110. Forexample, a clinician holding a PDA (e.g., device 210) taps or bumps thePDA on an infusion pump (e.g., device 110) to initiate an associationbetween the FDA and the infusion pump.

In another example, just shaking the device or moving the mobile devicein a specific pattern in a short time window can generate a gesture.

Detection of a request for association is achieved by physical contactwith a characteristic acceleration and deceleration patterns on bothdevices. In other words, a gesture, can be, but is not limited to, aphysical contact of device 210 with device 110, a pattern of a pluralityof physical contacts of device 210 with device 110.

A gesture can be user input on one device (e.g., pressing a key) inconcert with gesture on other device, or user inputs on both devices inconcert (e.g., holding a push button, touching a touch screen, etc).

As such, gesture sensor 115 detects the acceleration and deceleration ofthe gestures. Likewise, gesture sensor 215 detects the correspondingacceleration characteristics of the gestures.

In various embodiments, gesture sensors 115 and 215 senseacceleration/deceleration patterns based on, among other things, (1) 3Dmotion in a similar trajectory based on weight of the devices, (2)maxima and minima acceleration within the time window, and/or (3)detection of spike patterns. It should be appreciated thatacceleration/deceleration patterns sensed by gesture sensor 115 isopposite of the acceleration/deceleration patterns detected by gesturesensor 215. Additionally, gesture sensors 115 and 215 sense theacceleration/deceleration patterns within a small time window

Association gesture determiner 120 determines whether or not thegestures detected by gesture sensors 115 and 215 are associationgestures. In other words, some gestures may not be intended to associatethe devices and are therefore not association gestures. Accordingly, theunintended gestures or unauthorized gestures are filtered out by filter122. Moreover, the unauthorized gestures are logged in memory 158.

In one embodiment, association gesture determiner 120 determines whetheror not the gesture is an association gesture based on predefinedassociation gesture patterns. The predefined gesture patterns may bestored in memory 158, memory 258 and/or medical management system 112.

In another embodiment, association gesture determiner 120 determineswhether or not the detected gesture is an association gesture based ongesture information received from device 210. For example, the gesturepattern detected at device 210 is compared with the gesture patterndetected at device 110. If the detected gestures correspond and aredetected within the predefined time window (by both devices), then thedetected gestures are deemed as association gestures. If the detectedgestures do not correspond and are not detected within the predefinedtime window (by both devices), then the gestures are not deemed asassociation gestures and filtered out by filter 122.

In response to an association gesture, device associator 132 associatesdevices 110 and 210. In particular, association request validator 133 ofdevice associator 132 validates the association request. For example,association request validator 133 validates the association request whenan association gesture is detected, then mobile devices 110 and 210exchange information based on the system state, device class, securitypolicy and system configuration.

In response to an association gesture, clinician associator 134associates a clinician with device 110. For example, a clinician who islogged into a FDA is associated to device 110, in response to cliniciantapping the FDA on device 110. In particular, the gesture triggers adata transfer of clinician information from the mobile device to themedical device. The clinician information is then stored on the medicaldevice and is used in clinical functions. A subsequent gesture maytrigger a clinician log out and disassociation from the medical device.

In one embodiment, the clinician association is done when device 210 isready to transfer clinician information and when device 110 is ready toaccept clinician login.

It should be appreciated that it is desirable to be able to quicklyassociate a medical device with the clinician that is about to performtasks and modify the care given by the medical device. Also, informationabout who performed specific tasks on a patient is embedded in clinicalreports.

In response to an association gesture, patient associator 136 associatesa patient with device 110. For example, in response to a cliniciantapping a mobile device on a medical device, patient associator 136associates the patient with the medical device. In another example, whenmultiple infusion pumps are used for administrating care to a patient,it is required to distribute the patient information such as, patientidentification, patient weight, to the infusion pumps.

A medical device is often required to be configured for a specificpatient, usually by using a patient identifier and/or patient name. Themobile device can streamline the configuration of the patientidentifiers by allowing a clinician to transfer patient information fromthe mobile device by bumping the mobile device and the medical device.

In one embodiment, one of the devices does not include a gesturedetector. As such, the detection of a request for association can beachieved by close proximity between the devices andacceleration/deceleration patterns detected on the device with thegesture detector.

For example, device 210 includes gesture sensor 215 and device 120 doesnot include gesture sensor 115. In this embodiment, gesture sensor 215detects an association gesture and proximity determiner 240 searches fordevice 120 in close proximity to device 210. Device 210 alsocommunicates an intent to associate with device 110.

User interface 150 communicates information to a user of device 110.Similarly, user interface 250 communicates information to a user ofdevice 220. In general, display 151, speaker 153 and/or haptic feedbacksystem 154 provide information to a user regarding the process ofassociation between devices 110 and 210.

For example, display controller 152 controls the viewability of visualelements displayed on display 151. In such an example, information suchas text and/or buttons change color when an association occurs.

In another example, speaker 153 makes a sound to indicate that anassociation gesture has occurred. Similarly, haptic feedback system 154provides a tactile vibration to indicate that an association gesture hasoccurred.

FIG. 4 depicts an embodiment of a method 400 for associating a medicaldevice with a second device. In various embodiments, method 400 iscarried out by processors and electrical components under the control ofcomputer readable and computer executable instructions. The computerreadable and computer executable instructions reside, for example, in adata storage medium such as computer usable volatile and non-volatilememory. However, the computer readable and computer executableinstructions may reside in any type of computer readable storage medium.In some embodiments, method 400 is performed at least by device 110and/or device 210, as described in FIGS. 1-3.

At 410 of method 400, a gesture of the second device with respect to themedical device is detected, wherein the detecting the gesture is withina predefined time window. For example, a taping of device 210 withrespect to device 110 is detected by gesture sensor 115 within apredefined time window of 10 seconds.

In one embodiment, at 412, the gesture of a mobile device with respectto the medical device is detected. For example, the tapping of a PDA onan infusion pump to indicate a request for association between the FDAand the infusion pump is detected.

In another embodiment, at 414, the gesture is detected at the seconddevice. For example, the tapping (e.g., a single or multiple taps) ofthe FDA on the infusion pump is detected by an accelerometer in the FDA.

In a further embodiment, at 416, the gesture is detected at the medicaldevice. For example, the tapping of the FDA on the infusion pump isdetected by an accelerometer in the infusion pump.

At 420, the gesture is determined to be an association gesture forinitiating a request to associate the medical device with the seconddevice. For example, association gesture determiner 120 determines thatthe tapping of the FDA on the infusion pump is a request to associatethe FDA with the infusion pump.

At 430, the medical device is associated with the second device based onthe association gesture. For example, an infusion pump is associatedwith another infusion pump based on an association gesture.

At 440, information related to the detected gesture is communicated withthe second device. For example, information related to a gesture betweena FDA and an infusion pump is exchanged between the FDA and the infusionpump.

In one embodiment, at 442, information related to the detected gestureis received at the medical device from the second device. For example,the acceleration pattern of the gesture detected at the FDA iswirelessly transmitted to the infusion pump.

In another embodiment at 444, information related to the detectedgesture is received at the second device from the medical device. Forexample, the acceleration pattern of the gesture detected at theinfusion pump is wirelessly transmitted to the FDA.

At 450, a proximity between the medical device and the second device isdetermined. For example, one of the devices does not include anaccelerometer or gyroscope. As such, the detection of a request forassociation can be achieved by the proximity between the devices andacceleration/deceleration patterns detected on the device with thegesture detector.

At 460, an unauthenticated gesture is filtered out. For example, filter122 filters out an unintended physical contact between a FDA and aninfusion pump.

At 470, the association request based on information communicated withthe medical device is validated. For example, association requestvalidator 133 validates that an association request between a mobiledevice and medical device based, in part, that a mutual bump wasdetected.

Embodiments of Exchanging Data Between Devices

The discussion provided below will first describe the components and/orfeatures of devices 110 and 210 in relation to the exchange ofinformation. Then the discussion will describe the functionality of thecomponents and/or features during use of the devices in the medicalenvironment. In particular, the discussion will describe thefunctionality of the components and/or features regarding the exchangingof information between the devices to facilitate in operations performedby one or more of devices 110 and 210.

Referring now to FIGS. 1-3, device 110 further includes operationdeterminer 160. Operation determiner 160 includes operation dataaccessor 162, mode controller 164, privilege determiner 166 and devicestate determiner 168.

Operation determiner 160 is for determining operations or tasks to beperformed in response to a gesture performed between devices 110 and210. It should be appreciated that one gesture can result in multipleoperations.

Operation data accessor 162 is for accessing operation data tofacilitate in the operation to be performed by device 110. Modecontroller 164 is for controlling a mode of device 110 based on thegesture. Privilege determiner 166 is for determining privileges of aclinician. Device state determiner 168 is for determining the devicestate of device 110.

Similar to device 110, device 210 includes operation determiner 260operation data accessor 262, mode controller 264, privilege determiner266, and device state determiner 268.

The components included in device 210 are the same components andfunction similarly as the components of device 110. However, for brevityand clarity, the description herein will focus on the components ofdevice 110.

Devices 110 and 210 must be associated such that they properly andsafely exchange information with one another. In general, after theassociation phase, devices 110 and 210 exchange information about theoperations their respective states allow. The receiving side thenperforms zero or more of the allowed operations. There is no limitationin how many operations can be performed based on a single associationgesture. The available operations can be based on what is currentlydisplayed on the user interfaces, alarm state, device state, andphysical or logical location, etc. Therefore, the exchanged informationfacilitates in the performing of operations by one or more of devices110 and 210.

The information exchanged between the devices can facilitate indetermining the operation to be performed by the devices. For example,devices 110 and 210 exchange information (via wireless communicationmodules 145 and 245) based on the system state, device class, securitypolicy and system configuration. Accordingly, operation determiner 160determines what operations are to be performed by device 110.

In general, the operations determined to be performed by the devices caninclude, but are not limited to, an operation performed in response to agesture, an operation performed based on subsequent accessing ofoperation data, or an operation performed in response to bi-directionalrequest of operation data between devices 110 and 210.

Moreover, the different types of operations are typically not authorizedat all times. This depends on multiple factors, such what screen theclinician is viewing on the mobile device, and what state the medicaldevice is in. Multiple operations may be performed in response to asingle gesture. For example, transferring historical logs are done as aresult of a single tap that also performs clinician login.

In particular, operation data accessor 162 can access operational datafrom device 210 to facilitate in the operations to be performed bydevice 110. Operation data accessor 162 can also access operational datastored on memory 158, memory 258 and/or medical management system 112.Moreover, operational data accessor 162 can access (e.g., receive, send)data via wireless communication module 145.

It should be appreciated that the information exchanged between thedevices can occur before, during or after the performing of theoperation. In one embodiment, operational information can be collectedat run time from sensors on the medical device and transferred to themobile device.

Various types of information related to the operations can be exchangedbetween the devices. Moreover, the exchanged information can be based onthe system state, device class, security policy and systemconfiguration.

The exchanged information can include, among other things, a transfer ofdata that forms an infusion order to the medical device from the mobiledevice; a transfer of historical logs from the medical device to themobile device; a transfer of infusion status from the medical device tothe mobile device; a transfer of device configuration from the mobiledevice to the medical device; a transfer of device configuration fromthe mobile device to the medical device; a transfer of calibrationparameters from the mobile device to the medical device; a transfer ofdataset profile, including care area, from the mobile device to themedical device; a transfer of data to wake up the medical device from apower save mode; a transfer of data to place the medical device into apower save mode; a transfer of data to silence an alarm on the medicaldevice; and a transfer of configuration data, including software andfirmware to perform device update (configuration update is for devicesynchronization and also applies to all device configuration changes).

It should be appreciated that the exchange of information can be inresponse to an association gesture between devices 110 and 210 and thestate of the devices.

In particular, a mobile device can be used to collect and prepareinformation related to programming of a medical device. This can be anorder transferred to the mobile device from a pharmacy system, an ordercreated on the local user interface of the mobile device, or justprogramming parameters entered on the mobile device. Once an order orprogramming parameters are ready to be transferred to the medicaldevice, the clinician can provide an association gesture (e.g., a bump)between the mobile device and the medical device and the transfer of theprogramming data is initiated. Once the programming data is transferredto the medical device, the operation of the program can be executed.

A mobile device can collect data from the medical device when anassociation gesture is detected. The collected data may includehistorical logs, system status, infusion status, clinical event logs,etc. The association gesture can also synchronize information such aspatient status information.

The mobile device can be used to configure the medical device with drugdata sets, calibration data, and configuration parameters. This data canbe transferred when an association gesture is detected.

Privilege determiner 168 determines the privileges of the clinician thatis logged into device 210 and associated to device 110. Accordingly, theoperations to be performed and the information exchanged are dependenton the privileges of the user. For example, operation determiner 160determines what operations are able to be performed based on theprivileges of the user. Moreover, operation data accessor 162 accessesdata based on the privileges of the user.

Device state determiner 168 determines the state of the devices.Accordingly, the operations to be performed and the informationexchanged are dependent on the state of the devices. For example,operation determiner 160 determines what operations are able to beperformed based on the state of either device or the aggregate state ofthe devices. Moreover, operation data accessor 162 accesses data basedon the state of the devices.

It should be appreciated that a gesture can be used to wake up a medicaldevice from a suspended mode (or state), or a sleep mode. A gesture canalso put a device back into sleep mode or a power save mode. When themedical device is in an alarm state, a gesture with a mobile devicesilences the alarm.

FIG. 5 depicts an embodiment of a method 500 for performing an operationby a medical device. In various embodiments, method 500 is carried outby processors and electrical components under the control of computerreadable and computer executable instructions. The computer readable andcomputer executable instructions reside, for example, in a data storagemedium such as computer usable volatile and non-volatile memory.However, the computer readable and computer executable instructions mayreside in any type of computer readable storage medium. In someembodiments, method 500 is performed at least by device 110 and/ordevice 210, as described in FIGS. 1-3.

At 510, an operation is determined to be performed by the medicaldevice, wherein the determination is in response to a gesture of asecond device with respect to the medical device. For example, aninfusion operation is determined to be performed by an infusion pump inresponse to a gesture of a PDA with respect to the infusion pump.

At 520, operation data is accessed for the operation performed by themedical device. For example, parameters for the infusion operation aretransmitted to the medical device from the FDA.

In one embodiment, at 522, operation data is accessed by the medicaldevice. For example, patient weight is transmitted by the medicaldevice.

In another embodiment, at 524, operation data is accessed by the seconddevice. For example, historical logs from the medical device areaccessed by the mobile device.

In a further embodiment, at 526, operation data is accessed from amedical management system. For example, historical logs are transmittedfrom the medical management system to the mobile device and/or themedical device.

At 530, the operation performed is based, in part, on the gesture.

In one embodiment, at 532, the operation is performed in response to thegesture. For example, an operation of infusing medication to a patientis performed in response to tapping of the FDA onto the infusion pump.

In another embodiment, at 534, the operation is performed subsequent theaccessing of the operation data. For example, the operation of infusingmedication is performed after historical logs are transmitted to mobiledevice.

In a further embodiment, at 536, the operation is performed in responseto a bi-directional request of the operation data between the medicaldevice and the second device.

At 540, user privileges are determined, wherein the determining anoperation to be performed by the medical device is based, in part, onthe privileges. For example, the operation of infusing medication to apatient is based, in part, on the privilege of a doctor who is loggedinto the mobile device.

At 550, determine a state of the medical device, wherein the determiningan operation to be performed by the medical device is based, in part, onthe state of the device.

At 560, a mode of the medical device is controlled based on the gesture.For example, the mode of the medical device is changed from sleep modeto active mode in response to the gesture.

Various embodiments of the present invention are thus described. Whilethe present invention has been described in particular embodiments, itshould be appreciated that the present invention should not be construedas limited by such embodiments, but rather construed according to thefollowing claims.

1. A medical device comprising: an operation determiner for determiningoperations to be performed by said medical device in response to agesture of a second device with respect to said medical device, whereinsaid gesture is sensed by a gesture sensor selected from a groupconsisting of: an accelerometer and a gyroscope; and an operation dataaccessor for accessing operation data for said operation performed bysaid medical device.
 2. The medical device of claim 1, wherein saidoperation comprises: an operation performed in response to said gesture.3. The medical device of claim 1, wherein said operation comprises: anoperation performed based on subsequent accessing of said operationdata.
 4. The medical device of claim 1, wherein said operationcomprises: an operation performed in response to bi-directional requestof said operation data between said medical device and said seconddevice.
 5. The medical device of claim 1, further comprising: memory forstoring said operation data.
 6. The medical device of claim 1, furthercomprising: a mode controller for controlling a mode of said medicaldevice based on said gesture.
 7. The medical device of claim 1, furthercomprising: a privilege determiner for determining privileges of a user.8. The medical device of claim 1, wherein said operation determinerfurther comprising: a device state determiner for determining a state ofsaid medical device, wherein said determining said operation to beperformed by said medical device is based, in part, on said state ofsaid medical device.
 9. A mobile device comprising: an operationdeterminer for determining an operation to be performed by a medicaldevice in response to a gesture of said mobile device with respect tosaid medical device, wherein said gesture is sensed by a gesture sensorselected from a group consisting of: an accelerometer and a gyroscope;and an operation data accessor for accessing operation data for saidoperation performed by said medical device.
 10. The mobile device ofclaim 9, wherein said operation comprises: an operation performed inresponse to said gesture.
 11. The mobile device of claim 9, wherein saidoperation comprises: an operation performed based on subsequentaccessing of said operation data.
 12. The mobile device of claim 9,wherein said operation comprises: an operation performed in response tobi-directional request of said operation data between said medicaldevice and a second device.
 13. The mobile device of claim 9, furthercomprising: memory for storing said operation data.
 14. The mobiledevice of claim 9, further comprising: a mode controller for controllinga mode of said medical device based on said gesture.
 15. The mobiledevice of claim 9, further comprising: a privilege determiner fordetermining privileges of a user.
 16. The mobile device of claim 9,wherein said operation determiner further comprising: a device statedeterminer for determining a state of said medical device, wherein saiddetermining said operation to be performed by said medical device isbased, in part, on said state of said medical device.
 17. A method forperforming an operation by a medical device, said method comprising:determining an operation to be performed by said medical device, whereinsaid determination is in response to a gesture of a second device withrespect to said medical device, wherein said gesture is sensed by agesture sensor selected from a group consisting of: an accelerometer anda gyroscope; accessing operation data for said operation performed bysaid medical device; and performing said operation based, in part, onsaid gesture.
 18. The method of claim 17, wherein said accessingoperation data for operation performed by said medical device comprises:accessing operation data by said medical device.
 19. The method of claim17, wherein said accessing operation data for operation performed bysaid medical device comprises: accessing operation data by said seconddevice.
 20. The method of claim 17, wherein said accessing operationdata for operation performed by said medical device comprises: accessingoperation data from a medical management system.
 21. The method of claim17, wherein said performing said operation based, in part, on saidgesture comprising: performing said operation in response to saidgesture.
 22. The method of claim 17, wherein said performing saidoperation based, in part, on said gesture comprising: performing saidoperation subsequent said accessing of said operation data.
 23. Themethod of claim 17, wherein said performing said operation based, inpart, on said gesture comprising: performing said operation in responseto a bi-directional request of said operation data between said medicaldevice and said second device.
 24. The method of claim 17, furthercomprising: determining user privileges, wherein said determining anoperation to be performed by said medical device is based, in part, onsaid privileges.
 25. The method of claim 17, further comprising:determining a state of said medical device, wherein said determining anoperation to be performed by said medical device is based, in part, onsaid state of said device.
 26. The method of claim 17, furthercomprising: controlling a mode of said medical device based on saidgesture.